-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for URL wildcards and exact URL #9835
base: develop
Are you sure you want to change the base?
Add support for URL wildcards and exact URL #9835
Conversation
Hi, I received the invitation to test the new feature. What I'm doing wrong? Regards. |
You'll have to download the original branch and compile it yourself. There's no snapshots for separate commits or PR's. |
Ah OK. |
Hi, I was able to download and compile it in RHEL, it seems to work! |
Hi, I'm trying to build an AppImage to test the app on my daily computer but after a successful build on Arch Linux I can' t get any .AppImage file in the source directory. Configure with "-DKEEPASSXC_DIST_TYPE=AppImage" switch is not enough? |
Use the release-tool |
I tried but I got this error: [matteo@arch keepassxc]$ ./release-tool build -v develop --appimage [ INFO ] Checking out release tag 'develop'... Update the VERSION argument value or use a ... suffix to tell -- Found Git HEAD Revision: cd7a53a -- Setting up build for KeePassXC v2.8.0 -- Including translations... -- Using asciidoctor: /usr/bin/asciidoctor
-- Disabled features: -- Configuring done (0.1s) Maybe I missed some steps... |
TODO: Check if using https://doc.qt.io/qt-6/qregularexpression.html#wildcardToRegularExpression is preferred after Qt6 upgrade. Qt5 does not support |
Oh nice that will likely replace one of our tools functions. |
e72c373
to
229704d
Compare
229704d
to
9ab03a5
Compare
Adds support for URL wildcards and exact URL if the address is wrapped insinde
"
e.g."https://example.com/page.php"
. Without wildcards, URL's are handled normally with the old/current implementation.The wildcards can be used freely, and some example addresses are:
https://*.example.com/page/*
https://192.*.168.1/
subdomain.of.*.example.com/page/*/login
Fixes #3718.
Testing strategy
Manually, and added automatic tests.
Type of change